Method and device for managing tab window indicating application group including heterogeneous applications

ABSTRACT

A method and a device for managing a tab window indicating a group including heterogeneous applications. The method includes outputting a display window comprising at least one or more objects for executing one or more applications on a terminal window, receiving a user input that selects the at least one or more objects and moves the selected at least one or more objects to a region excluding the display window, generating an application group comprising at least one or more applications corresponding to the selected at least one or more objects according to the received user input, and outputting a tab window indicating the generated application group to the terminal window.

CROSS-REFERENCE TO RELATED APPLICATION(S)

This application is a continuation application of prior application Ser.No. 14/994,883, filed on Jan. 13, 2016, which has issued as U.S. Pat.No. 10,705,689 on Jul. 7, 2020 and is a continuation of an Internationalapplication number PCT/KR2014/006538 filed on Jul. 18, 2014, whichclaimed the benefit of a Korean patent application number10-2013-0092240 filed on Aug. 2, 2013 in the Korean IntellectualProperty, the entire disclosure of each of which is hereby incorporatedby reference.

TECHNICAL FIELD

The present disclosure relates to a method and device for managing a tabwindow indicating a group including heterogeneous applications.

BACKGROUND

In general, a touch screen refers to a screen capable of receiving atouch input. The touch screen may perform a function of receiving thetouch input by adding a touch panel to a display, and may be utilized invarious ways owing to its convenience of use. As a central processingunit (CPU), a memory, and a display device are developed, a multi-windowenvironment in which a terminal including the touch screen maysimultaneously execute a plurality of applications has become morecommon.

However, a size of a terminal screen is limited, and the terminalmanages an execution screen of an application in a window unit, whichmay deteriorate readability of the terminal when the plurality ofapplications are executed. When the plurality of applications areexecuted, a user may have difficulty in individually controlling theplurality of applications.

Therefore, when the plurality of applications installed in the terminalare executed, there is a demand for a technology for effectivelymanaging windows of the executed applications.

The above information is presented as background information only toassist with an understanding of the present disclosure. No determinationhas been made, and no assertion is made, as to whether any of the abovemight be applicable as prior art with regard to the present disclosure.

SUMMARY

Aspects of the present disclosure are to address at least theabove-mentioned problems and/or disadvantages and to provide at leastthe advantages described below. Accordingly, an aspect of the presentdisclosure is to provide a method and device for managing a tab windowindicating a group including heterogeneous applications.

Another aspect of the present disclosure is to provide a non-transitorycomputer-readable recording medium having recorded thereon a program forexecuting the method.

Additional aspects will be set forth in part in the description whichfollows and, in part, will be apparent from the description, or may belearned by practice of the presented embodiments.

In accordance with an aspect of the present disclosure, a method ofmanaging a tab window is provided. The method includes outputting adisplay window including at least one or more objects for executing oneor more applications on a terminal window, receiving a user input thatselects the at least one or more objects and moves the selected at leastone or more objects to a region excluding the display window, generatingan application group including at least one or more applicationscorresponding to the selected at least one or more objects according tothe received user input, and outputting a tab window indicating thegenerated application group to the terminal window.

In accordance with another aspect of the present disclosure, a devicefor managing a tab window is provided. The device includes an input unitconfigured to receive a user input that selects at least one or moreobjects for executing at least one or more applications and to move theselected at least one or more objects to a region excluding a displaywindow, a group generating unit configured to generate an applicationgroup including applications corresponding to the selected objectaccording to the received user input, and an output unit configured tooutput a display window including at least one or more objects and tooutput a tab window indicating the generated application group.

In accordance with another aspect of the present disclosure, a method ofmanaging a tab window is provided. The method includes selecting atleast one or more applications from applications installed in aterminal, generating a group including the selected at least one or moreapplications, determining a layout of a tab window indicating thegenerated group, and storing information regarding the generated groupbased on the selected at least one or more applications and thedetermined layout.

In accordance with another aspect of the present disclosure, a devicefor managing a tab window is provided. The device includes a groupgenerating unit configured to select at least one or more applicationsfrom applications installed in a terminal and to generate a groupincluding the selected at least one or more applications, a framechanging unit configured to determine a layout of a tab windowindicating the generated group, and a storage unit configured to storeinformation regarding the generated group based on the selected at leastone or more applications and the determined layout.

In accordance with another aspect of the present disclosure, anon-transitory computer-readable storage medium storing a computerprogram for executing the method described above is provided.

Other aspects, advantages, and salient features of the disclosure willbecome apparent to those skilled in the art from the following detaileddescription, which, taken in conjunction with the annexed drawings,discloses various embodiments of the present disclosure.

BRIEF DESCRIPTION OF THE DRAWINGS

The above and other aspects, features, and advantages of certainembodiments of the present disclosure will be more apparent from thefollowing description taken in conjunction with the accompanyingdrawings, in which:

FIG. 1 is a flowchart of an example of a method of managing a tab windowaccording to an embodiment of the present disclosure;

FIGS. 2A to 2E illustrate examples in which a device generates tabwindows and displays the tab windows on a terminal screen according tovarious embodiments of the present disclosure;

FIGS. 3A and 3B illustrate other examples in which a device generatestab windows and displays the tab windows on a terminal screen accordingto various embodiments of the present disclosure;

FIG. 4 illustrates an example in which a device displays objectsindicating a tab window on a terminal screen according to an embodimentof the present disclosure;

FIG. 5 illustrates an example in which a device displays tab windows ona terminal screen according to an embodiment of the present disclosure;

FIG. 6 is a flowchart of another example of a method of managing a tabwindow according to an embodiment of the present disclosure;

FIGS. 7A and 7B illustrate examples in which a device displays anexecution screen of one of applications included in a tab window on aterminal screen according to various embodiments of the presentdisclosure;

FIG. 8 is a flowchart of another example of a method of managing a tabwindow according to an embodiment of the present disclosure;

FIGS. 9A to 9C illustrate examples in which a device displays changedtab windows on a terminal screen according to various embodiments of thepresent disclosure;

FIG. 10 is a flowchart of another example of a method of managing tabwindows according to an embodiment of the present disclosure;

FIGS. 11A to 11D illustrate examples in which a device converts anddisplays execution screens of a plurality of applications to a tabwindow mode according to various embodiments of the present disclosure;

FIG. 12 is a flowchart of another example of a method of managing tabwindows according to an embodiment of the present disclosure;

FIG. 13 is a flowchart of another example of a method of managing tabwindows according to an embodiment of the present disclosure;

FIGS. 14A to 14C illustrate examples in which a device moves dataincluded in one tab window to another tab window according to variousembodiments of the present disclosure;

FIGS. 15A to 15C illustrate examples in which a device sets or changesenvironments of tab windows according to various embodiments of thepresent disclosure;

FIGS. 16A and 16B illustrate examples in which a device outputs a tabwindow on a terminal screen in a card view form according to variousembodiments of the present disclosure;

FIGS. 17A and 17B illustrate examples in which a device executes a tabwindow in a card view form when an application is executed according tovarious embodiments of the present disclosure;

FIGS. 18A to 18C illustrate examples in which a device manages a tabwindow in a card view form based on a user input of up and downscrolling according to various embodiments of the present disclosure;

FIGS. 19A to 19D illustrate examples in which a device manages a tabwindow in a card view form based on a user input of up and down and leftand right scrolling according to various embodiments of the presentdisclosure;

FIGS. 20A and 20B illustrate examples in which a device convertsexecution screens of applications included in a tab window in a cardview form according to various embodiments of the present disclosure;

FIGS. 21A and 21B illustrate examples in which a device manages a tabwindow in a card view form based on a user input of a long touch gestureaccording to various embodiments of the present disclosure;

FIG. 22 is a block diagram of elements of a device according to anembodiment of the present disclosure; and

FIG. 23 is a block diagram of an example of a window grouping managementarchitecture used by a device to manage a tab window according to anembodiment of the present disclosure.

Throughout the drawings, it should be noted that like reference numbersare used to depict the same or similar elements, features, andstructures.

DETAILED DESCRIPTION

The following description with reference to the accompanying drawings isprovided to assist in a comprehensive understanding of variousembodiments of the present disclosure as defined by the claims and theirequivalents. It includes various specific details to assist in thatunderstanding but these are to be regarded as merely exemplary.Accordingly, those of ordinary skill in the art will recognize thatvarious changes and modifications of the various embodiments describedherein can be made without departing from the scope and spirit of thepresent disclosure. In addition, descriptions of well-known functionsand constructions may be omitted for clarity and conciseness.

The terms and words used in the following description and claims are notlimited to the bibliographical meanings, but, are merely used by theinventor to enable a clear and consistent understanding of the presentdisclosure. Accordingly, it should be apparent to those skilled in theart that the following description of various embodiments of the presentdisclosure is provided for illustration purpose only and not for thepurpose of limiting the present disclosure as defined by the appendedclaims and their equivalents.

It is to be understood that the singular forms “a,” “an,” and “the”include plural referents unless the context clearly dictates otherwise.Thus, for example, reference to “a component surface” includes referenceto one or more of such surfaces.

It will be understood that when an element is referred to as being“connected” to another element, it may be “directly connected” to theother element or may be “electrically connected” to the other elementwith other element(s) interposed therebetween. It will also beunderstood that the terms “comprises”, “includes”, and “has”, when usedherein, specify the presence of stated elements, but do not preclude thepresence or addition of other elements, unless otherwise defined.

Throughout the specification, a term “gesture” refers to a user's actionused to control a terminal. For example, a gesture described in thespecification includes tap, touch and hole, double tap, drag, panning,flick, drag and drop, hand shaking, etc.

Throughout the specification, a “device” refers to an element that isincluded in a terminal and implements a predetermined objective. In thisregard, the terminal may include a mobile terminal including asmartphone but is not limited thereto. In more detail, the terminal maybe included in various embodiments of the present disclosure as long asthe terminal is an object that includes a screen capable of display andan interface that may receive input information from a user, receives auser input, and implements the predetermined objective.

Throughout the specification, “outputting of a screen of a device” meansdisplaying of a specific screen on the screen of the device. Thus,“outputting of a screen of a device” includes “displaying of a screen ofa device”.

FIG. 1 is a flowchart of an example of a method of managing a tab windowaccording to an embodiment of the present disclosure.

Referring to FIG. 1, the method of managing the tab window includesoperations that are time-serially performed by a device 2200 of FIG. 22or 23. Thus, although omitted below, a description of the device 2200 ofFIG. 22 or 23 that will be described later may apply to the method ofmanaging the tab window of FIG. 1.

In operation S110, the device 2200 outputs a display window including atleast one or more objects for executing a plurality of applications on aterminal screen.

An object refers to a graphic image (for example, an icon) that is setfor each of the applications. For example, a user may select an icondisplayed on the terminal screen, thereby executing an applicationcorresponding to the icon. However, the object may correspond to a titleof an application displayed on the terminal screen and theabove-described graphic image as well. In other words, the objectcorresponds to any form displayed on the terminal screen to execute theapplication without limitation.

The display window may be one of an application tray including theapplications installed in a terminal, and another tab window indicatinga previously generated application group. In this regard, theapplication tray refers to a window on which objects corresponding tothe applications installed in the terminal are aligned. The tab windowrefers to a window on which objects corresponding to applicationsincluded in the application group are aligned. In this regard, theapplication group refers to a set of applications included in one tabwindow.

In operation S120, the device 2200 selects the object and receives auser input that moves the selected object to a region excluding thedisplay window. In this regard, the user input may be a user touch inputthrough the terminal screen but is not limited thereto. In other words,the user input may be an input through a key pad (not shown) included inthe terminal and a separate input device (not shown) connected to theterminal.

In operation S130, the device 2200 generates an application groupincluding an application corresponding to the selected object accordingto the received user input. In this regard, the application group mayinclude a plurality of heterogeneous applications. For example, theheterogeneous applications include applications having differentexecution objectives or applications having different processes forexecuting the applications.

In operation S140, the device 2200 outputs the tab window indicating thegenerated application group on the terminal window.

Hereinafter, the method of managing the tab window described withreference to FIG. 1 above (in more detail, a method of generating thetab window and displaying the tab window on the terminal screen) willnow be described with reference to FIGS. 2 through 5.

FIGS. 2A to 2E illustrate examples in which the device 2200 generatestab windows 230, 240, 250, and 260 and displays the tab windows 230,240, 250, and 260 on a terminal screen according to various embodimentsof the present disclosure.

Referring to FIG. 2A, the device 2200 outputs a display window 210including at least one or more objects for executing a plurality ofapplications on the terminal screen. Referring to FIG. 2A, the displaywindow 210 is shown as an application tray. The objects (for example,icons) respectively corresponding to the applications installed in aterminal are aligned in the display window 210.

A user selects one of the objects included in the display window 210.For example, the user may touch one of the objects included in thedisplay window 210 or may move an object selected by drag and drop to aregion of the terminal screen excluding the display window 210.

Referring to FIG. 2B, the user selects an object 220 by touching theobject 220 from among the objects included in the display window 210.The device 2200 receives a user input that selects the object 220. Thedevice 2200 generates an application group including the applicationcorresponding to the object 220 selected according to the received userinput. The device 2200 outputs the tab window 230 indicating thegenerated application group on the terminal screen.

Referring to FIG. 2C, the user drags and drops the object 220 from amongthe objects included in the display window 210, and moves the selectedobject 220 to a region excluding the display window 210.

A process in which the device 2200 receives the user input, generatesthe application group, and outputs the tab window 240 on the terminalscreen is the same as described with reference to FIG. 2B. In thisregard, the tab window is displayed as a size corresponding to apreviously determined region 240.

Referring to FIG. 2C, although the selected object 220 and the tabwindow 240 are simultaneously displayed on one screen, this is merely anexample for description. In other words, an image of the selected object220 disappears from a location from which the selected object 220 ismoved, and the tab window 240 including the selected object 220 is onlyoutput on the terminal screen.

Referring to FIG. 2D, the tab window 250 indicating a previouslygenerated application group is displayed on the terminal screen. In thisregard, the operation described with reference to FIG. 2C above mayapply.

In more detail, the user drags and drops the object 220 of the objectsincluded in the display window 210 to a region excluding the displaywindow 210. Thereafter, the device 2200 generates an application groupincluding the application corresponding to the selected object 220, andoutputs the tab window 260 indicating the generated application group onthe terminal screen.

Referring to FIG. 2E, the tab window 250 indicating a previouslygenerated application group is displayed on the terminal screen. In thisregard, the user may touch the object 220 of the objects included in thedisplay window 210.

The device 2200 includes the application corresponding to the selectedobject 220 in the application group indicating the tab window 250. Thedevice 2200 may add and display 270 the object 220 selected by a usertouch to a title bar of the tab window 250.

Meanwhile, the device 2200 stores information regarding the tab windows230, 250, and 260. In this regard, the tab windows 230, 250, and 260includes a list of the applications included in the application group orregions of the tab windows 230, 250, and 260. In more detail, the device2200 stores information regarding applications included in the generatedapplication group or locations and sizes of the tab windows 230, 250,and 260 displayed on the terminal screen.

Thereafter, when an input that displays the tab windows 230, 250, and260 is received from the user, the device 2200 displays the tab windows230, 250, and 260 on the terminal screen by using the stored informationregarding the tab windows 230, 250, and 260.

FIGS. 3A and 3B illustrate other examples in which the device 2200generates tab windows 310 and 340 and displays the tab windows on aterminal screen according to various embodiments of the presentdisclosure.

Referring to FIGS. 3A and 3B, the device 2200 outputs the display window310 including at least one or more objects for executing a plurality ofapplications on the terminal screen. The display window 310 isillustrated as the tab window 310 in FIGS. 3A and 3B. The objects (forexample, titles of the applications) respectively corresponding to theapplications installed in a terminal are aligned in the display window310.

In other words, the display window 310 may refer to another tab windowindicating a previously generated application group. In this regard, thedevice 2200 may display the tab window on the terminal screen by usingpreviously stored information regarding the tab window as describedabove.

Referring to FIG. 3A, a user selects an object 320 of the objectsdisplayed on the display window 310. The user moves the selected object320 to a region 330 excluding the display window 310. For example, theuser may move the object 320 to the region 330 excluding the displaywindow 310 by dragging and dropping the object 320. In this regard, theobject 320 may be a predetermined region that displays the titles of theapplications as shown in FIG. 3A.

The device 2200 generates an application group including an applicationcorresponding to the selected object 320 according to a received userinput. In other words, the device 2200 may generate an applicationgroup, other than the previously generated application group, by usingthe application corresponding to the selected object 320.

FIG. 3B illustrates an example of displaying the different tab windows310 and 340 on the terminal screen. In other words, the device 2200 maysimultaneously display the tab window 310 indicating the previouslygenerated application group and the tab window 340 indicating theapplication group generated according to the user input.

Meanwhile, the selected object 320 described with reference to FIG. 3Aabove may be a plurality of objects 320. In other words, the user mayselect two or more objects from the objects displayed on the displaywindow 310 by multi-touch. In this case, the tab window 340 describedwith reference to FIG. 3B above includes applications corresponding tothe selected two or more objects.

As described above, the device 2200 may simultaneously display two ormore tab windows on a terminal screen, and thus the user may moreefficiently perform multi-tasking.

FIG. 4 illustrates an example in which the device 2200 displays objects420, 430, and 440 indicating a tab window on a terminal screen accordingto an embodiment of the present disclosure.

Referring to FIG. 4, the device 2200 may display the objects 420, 430,and 440 respectively indicating the tab window on a predetermined regionof the terminal screen. For example, the device 2200 may display theobjects 420, 430, and 440 respectively indicating the tab windows andobjects 450 indicating applications on an application tray 410. If thedevice 2200 generates a plurality of tab windows, the device 2200 maydisplay the objects 420, 430, and 440 respectively indicating the tabwindows on the terminal screen.

FIG. 5 illustrates an example in which the device 2200 displays tabwindows 510, 520, 530, and 540 on a terminal screen according to anembodiment of the present disclosure.

Referring to FIG. 5, the device 2200 may display the tab windows 510,520, 530, and 540 on the terminal screen. For example, the device 2200may receive an input in which a user sequentially touches objectsindicating a previously generated tab window and sequentially displaytab windows corresponding to the touched objects on the terminal screen.

In this regard, the device 2200 may display the tab windows 510, 520,530, and 540 on the terminal screen by using previously storedinformation regarding each of the tab windows 510, 520, 530, and 540. Inother words, the device 2200 displays a tab window on the terminalscreen by using a stored location and region of the tab window and astored execution screen of an application. In this regard, the storedlocation and region of the tab window may refer to a location and regionof the tab window at the time when the tab window ends, and the storedexecution screen of the application may refer to an execution screendisplayed at the time when the tab window ends.

FIG. 6 is a flowchart of another example of a method of managing a tabwindow according to an embodiment of the present disclosure.

Referring to FIG. 6, the method of managing the tab window includesoperations that are time-serially performed by the device 2200 of FIG.22 or 23. Thus, although omitted below, a description of the device 2200of FIG. 22 or 23 that will be described later may apply to the method ofmanaging the tab window of FIG. 6.

The flowchart of FIG. 6 includes the continuously performed operationsof FIG. 1.

In operation S1510, the device 2200 receives a user input that selectsan object for executing an application included in a tab window. In thisregard, the object is the same as described with reference to FIG. 3Aabove. The user input may be a user touch input through a terminalscreen but is not limited thereto as described above.

In operation S1610, the device 2200 executes the application accordingto the user input.

In operation S1710, the device 2200 outputs an execution screen of theexecuted application on the terminal screen. In this regard, theexecution screen is output on at least partial region of the tab window.

Hereinafter, the method of managing the tab window described withreference to FIG. 6 above (in more detail, a method of displaying theexecution screen of the application included in the tab window on theterminal screen) will now be described with reference to FIGS. 7A and7B.

FIGS. 7A and 7B illustrate examples in which the device 2200 displays anexecution screen of one of applications included in a tab window 710 ona terminal screen according to various embodiments of the presentdisclosure.

Referring to FIG. 7A, the tab window 710 is displayed on a partialregion of the terminal screen. A partial region 720 of the tab window710 displays objects 730 for executing the applications included in thetab window 710. Another partial region 740 of the tab window 710displays the execution screen of one of the applications included in thetab window 710.

A user selects an object 731 from the objects 730 for executing theapplications included in the tab window 710. For example, the user mayselect the object 731 by multi-touch.

The device 2200 executes an application corresponding to the object 731selected by the user. The device 2200 outputs the execution screen ofthe application on the terminal screen.

Referring to FIG. 7B, the execution screen of the application executedby the device 2200 is displayed on a partial region 750 of the tabwindow 710. In other words, if the user selects the object 731, and anew application is executed, the device 2200 converts the previouslydisplayed execution screen of the application into an execution screenof the new application executed according to a user input.

As described with reference to FIGS. 7A and 7B above, when one of theapplications included in the tab window 710 is executed, the executionscreen of the application is displayed without exceeding a regionindicating the tab window 710. Thus, if a plurality of tab windows isdisplayed on the terminal window, and regions indicating the displayedtab windows do not overlap, the user may see execution screens ofapplications executed in the tab applications without overlapping theexecution screens. Thus, the user may more efficiently performmulti-tasking.

FIG. 8 is a flowchart of another example of a method of managing a tabwindow according to an embodiment of the present disclosure.

Referring to FIG. 8, the method of managing the tab window includesoperations that are time-serially performed by the device 2200 of FIG.22 or 23. Thus, although omitted below, a description of the device 2200of FIG. 22 or 23 that will be described later may apply to the method ofmanaging the tab window of FIG. 8.

The flowchart of FIG. 8 includes the continuously performed operationsof FIG. 1.

In operation S1520, the device 2200 receives a user input that changes aregion occupying the tab window on a terminal screen.

In operation S1620, the device 2200 changes a location of the tab windowor reduces or increases the region of the tab window according to thereceived user input.

In operation S1720, the device 2200 outputs the tab window on theterminal screen. In this regard, the output tab window refers to aresult obtained by reflecting a location change of the tab window or aregion change thereof that is performed in operation S1620.

Hereinafter, the method of managing the tab window described withreference to FIG. 8 above (in more detail, a method of displaying thechanged tab window on the terminal screen) will now be described withreference to FIGS. 9A to 9C.

FIGS. 9A to 9C illustrate examples in which the device 2200 displayschanged tab windows 930, 950, and 970 on a terminal screen according tovarious embodiments of the present disclosure.

Referring to FIGS. 9A to 9C, the device 2200 changes locations orregions of tab windows. In more detail, FIG. 9A illustrates an examplein which the device 2200 changes a location of the tab window 930, andFIGS. 9B and 9C illustrate examples in which the device 2200 changesregions of the tab windows 950 and 970.

Referring to a top figure of FIG. 9A, a user may drag a predeterminedregion 920 of a tab window 910 displayed on the terminal screen in amoving direction while touching the predetermined region 920. In thisregard, the predetermined region 920 may be a region that displaystitles of applications included in a tab window but is not limitedthereto.

Referring to a bottom figure of FIG. 9A, the device 2200 changes thelocation of the tab window 930 corresponding to a dragging direction anddisplays the changed location of the tab window 930 on the terminalscreen.

Referring to a top figure of FIG. 9B, the user may touch an object 940displayed on a part of the tab window 910 that is displayed on theterminal screen. In this regard, the object 940 refers to a graphicimage that may reduce or increase the region of the tab window 910.

Referring to a bottom figure of FIG. 9B, the device 2200 may increase orreduce a region indicating the tab window 950 according to a user touch.In more detail, when the tab window 950 is displayed on only a part ofthe terminal screen, the device 2200 increases and displays the tabwindow 950 to a whole of the terminal screen. When the tab window 950 isdisplayed on the whole of the terminal screen, the device 2200 reducesand displays the tab window 950 to a part of the terminal screen.

Referring to a top figure of FIG. 9C, a user may drag the region of thetab window 910 in a changing direction while touching a predeterminedlocation 960 of the tab window 910 displayed on the terminal screen. Inthis regard, the predetermined location 960 may be an edge of the tabwindow but is not limited thereto.

Referring to a bottom figure of FIG. 9C, the device 2200 changes aregion of the tab window 970 corresponding to a dragging direction anddisplays the changed region of the tab window 970 on the terminalscreen. In more detail, when the user drags the tab window 970 to theinside of a region currently occupying the tab window 910, the device2200 reduces and displays the region of the tab window 970. When theuser drags the tab window 970 to the outside of the region currentlyoccupying the tab window 910, the device 2200 increases and displays theregion of the tab window 970.

Meanwhile, the device 2200 stores information regarding a changedlocation or region of a tab window. In more detail, the device 2200renews and stores previously stored information regarding a location ora region of the tab window to information regarding the changed locationor region. Thus, if the location or the region of the tab window ischanged, the tab window is terminated and then is executed again, andthe device 2200 displays the tab window on the terminal screen by usingthe renewed information.

FIG. 10 is a flowchart of another example of a method of managing tabwindows according to an embodiment of the present disclosure.

Referring to FIG. 10, the method of managing the tab windows includesoperations that are time-serially performed by the device 2200 of FIG.22 or 23. Thus, although omitted below, a description of the device 2200of FIG. 22 or 23 that will be described later may apply to the method ofmanaging the tab window of FIG. 10.

The flowchart of FIG. 10 includes the continuously performed operationsof FIG. 1.

In operation S180, the device 2200 outputs another tab window on asecond region that is distinguished from a first region that displays atab window on a terminal screen. In this regard, the other tab window isnot a tab window that is already output on the terminal screen but is atab window indicating a previously generated application group.

Hereinafter, the method of managing the tab window described withreference to FIG. 10 above (in more detail, a method of displaying aplurality of tab windows on the terminal screen) will now be describedwith reference to FIGS. 11A to 11D.

FIGS. 11A to 11D illustrate examples in which the device 2200 convertsand displays execution screens 1110, 1120, 1130, and 1150 of a pluralityof applications to a tab window mode according to various embodiments ofthe present disclosure.

Referring to FIG. 11A, the execution screens 1110, 1120, 1130, and 1150of the applications are displayed on a terminal screen. Hereinafter,examples of converting the execution screens 1110, 1120, 1130, and 1150displayed on the terminal screen to the tab window mode will now bedescribed with reference to FIGS. 11A to 11D. In this regard, the tabwindow mode may correspond to a cascade mode, a dual mode, etc. but isnot limited thereto. In other words, the tab window mode may correspondto any types of modes that may display the execution screens 1110, 1120,1130, and 1150 according to a predetermined rule without limitation.

Referring to FIGS. 11A and 11B, when a user touches a “tab view” 1160among objects displayed on a predetermined region 1140 of the terminalscreen, the device 2200 may collect and display the execution screens1110, 1120, 1130, and 1150 on a single tab window 1165. In this regard,when the user touches the “tab view” 1160, the device 2200 separates anddisplays the tab window 1165 into the execution screens 1110, 1120,1130, and 1150. In other words, when the user touches the “tab view”1160, the device 2200 turns on or off a tab mode.

Referring to FIGS. 11B and 11C, when the user touches a “dual view” 1170among the objects displayed on the predetermined region 1140 of theterminal screen, the device 2200 converts and displays the tab window1165 to the dual mode. An example in which the device 2200 displays thetab window 1165 in the dual mode.

For example, the device 2200 may split the terminal screen into tworegions 1171 and 1173 and display an execution screen of each of aplurality of applications included in the tab window 1165 on one of theregions 1171 and 1173. In other words, if four applications are includedin the tab window 1165, the device 2200 may display two executionscreens on the left region 1171 and two execution screens on the rightregion 1173.

As another example, the device 2200 may split the terminal screen intothe two regions 1171 and 1173 and display the tab window 1165 on one ofthe regions 1171 and 1173. Thereafter, when the user executes a newapplication, the device 2200 may display an execution screen of theexecuted new application on the other one of the regions 1171 and 1173.

Referring to FIGS. 11C and 11D, when the user touches a “cascade view”1180 among the objects displayed on the predetermined region 1140 of theterminal screen, the device 2200 converts and displays the tab window1165 to the cascade mode.

For example, if four applications are included in the tab window 1165,the device 2200 may generate four tab windows 1191, 1192, 1193, and 1194respectively including the four applications, and display the generatedtab windows 1191, 1192, 1193, and 1194 on the terminal screen in acascade form.

In this regard, when the user touches the “tab view” 1160 again, thedevice 2200 may separate and display the tab window 1165 into theexecution screens 1110, 1120, 1130, and 1150 again.

As described above, the user may freely convert the execution screens1110, 1120, 1130, and 1150 of the applications to the tab window mode.Thus, the user may more effectively perform multi-tasking.

FIG. 12 is a flowchart of another example of a method of managing tabwindows according to an embodiment of the present disclosure.

Referring to FIG. 12, the method of managing the tab windows includesoperations that are time-serially performed by the device 2200 of FIG.22 or 23. Thus, although omitted below, a description of the device 2200of FIG. 22 or 23 that will be described later may apply to the method ofmanaging the tab windows of FIG. 12.

The flowchart of FIG. 12 includes the continuously processed operationsof FIG. 10. In other words, the method of managing the tab windows ofFIG. 12 includes operations that are performed when the tab windows aredisplayed on a terminal screen.

In operation S1810, the device 2200 receives a user input that moves anobject corresponding to an application included in one of the tabwindows to another tab window. In this regard, the user input maycorrespond to dragging and dropping an object corresponding to anapplication included in the one tab window and moving the object to theother tab window. The user input will be described in detail withreference to FIGS. 15A and 15B later.

In operation S1820, the device 2200 renews an application groupindicating each of the tab windows according to the received user input.In more detail, the device 2200 may renew the application group byexcluding the application corresponding to the moved object from anapplication group included in one of the tab windows and adding theapplication to an application included in the other tab window.

In operation S1830, the device 2200 renews and outputs the tab windowsbased on the renewed application group on the terminal screen. In moredetail, the device 2200 may correct and output an application listdisplayed on each of the tab windows by using information regarding theapplication group renewed in operation S1820 on the terminal screen.

The device 2200 stores information regarding the renewed tab windows. Inthis regard, the information regarding the tab windows may refer to alist of applications included in the renewed application group orregions of the two windows. In more detail, the device 2200 storesinformation regarding applications included in a generated applicationgroup or information regarding locations and sizes of tab windowsdisplayed on the terminal screen.

The method described with reference to FIG. 12 above corresponds to amethod of exchanging applications between a plurality of tab windows. Inother words, the device 2200 may move an application included in one ofthe plurality of tab windows based on a user gestures to another tabwindow.

The device 2200 may independently generate a new tab window by using theapplication included in one of the tab windows. In more detail, themethod in which the device 2200 generates the new tab window by usinginformation regarding moving of an object corresponding to theapplication included in one of the tab windows is the same as describedwith reference to FIGS. 3A and 3B.

According to various embodiments, the applications may be exchangedbetween the plurality of tab windows and data included in theapplications may also be exchanged as well. A method of exchanging thedata included in the applications between the plurality of tab windowswill be described in detail with reference to FIG. 13 later.

FIG. 13 is a flowchart of another example of a method of managing tabwindows according to an embodiment of the present disclosure.

Referring to FIG. 13, the method of managing the tab windows includesoperations that are time-serially performed by the device 2200 of FIG.22 or 23. Thus, although omitted below, a description of the device 2200of FIG. 22 or 23 that will be described later may apply to the method ofmanaging the tab windows of FIG. 13.

The flowchart of FIG. 13 includes the continuously processed operationsof FIG. 10. In other words, the method of managing the tab windows ofFIG. 13 includes operations that are performed when the tab windows aredisplayed on a terminal screen.

In operation S1840, the device 2200 executes an application included inone of the tab windows based on input information of a user. Forexample, the device 2200 may execute the application based oninformation regarding an object, which is selected by the user, forexecuting the application.

In operation S1850, the device 2200 receives a user input that moves anobject indicating data included in the executed application to anapplication included in another tab window. In this regard, the userinput is the same as described with reference to operation S1810 of FIG.12 above. In other words, the user input may correspond to dragging anddropping an object indicating data included in one of the tab windowsand moving the object to a point where the object of the applicationincluded in the other tab window is located. Alternatively, the userinput may correspond to dragging and dropping the object indicating dataincluded in one of the tab windows and moving an execution screen of theapplication displayed on the other tab window.

In operation S1860, the device 2200 executes the data in the applicationincluded in the other tab window according to the received user input.For example, if the data moved by the user input is a music reproductionfile, and the application included in the other tab window is a musicreproduction application, the device 2200 reproduces the moved musicreproduction file.

In operation S1870, the device 2200 outputs an execution screen of theexecuted application on the terminal screen. In more detail, anexecution screen according to reproduction of music is output on theother tab window (i.e., the tab window including the music reproductionapplication) in the example described above.

Hereinafter, the method of managing the tab windows described withreference to FIGS. 12 and 13 above (in more detail, a method of movingan application or data from one tab window to another tab window) willnow be described with reference to FIGS. 14A to 14C.

FIGS. 14A to 14C illustrate examples in which the device 2200 moves dataincluded in one of tab windows 1410 and 1420 to the other of the tabwindows 1410 and 1420 according to various embodiments of the presentdisclosure.

Referring to FIGS. 14A and 14B, an example of moving data of anapplication included in the tab window 1410 to the tab window 1420 isillustrated. Referring to FIG. 14C, an example of moving data between aplurality of applications included in the tab window 1410 isillustrated.

Although an example of the method of moving data described withreference to FIG. 13 above is illustrated in FIGS. 14A to 14C, theexample may apply to the method of moving an application described withreference to FIG. 12 above. In other words, a mechanism of moving datathat will be described with reference to FIGS. 14A to 14C is the same asthat of moving the application described with reference to FIG. 12above. Thus, a detailed description of the method of moving theapplication will not be repeated hereinafter.

Referring to FIG. 14A, a user performs an input that executes anapplication included in the tab window 1410. In this regard, a method inwhich the user executes the application is the same as described above.

Thereafter, the user performs an input that moves an object 1430indicating data included in the executed application to an applicationincluded in the tab window 1420. For example, the user may drag and dropthe object 1430 to the location of objects 1440 indicating titles ofapplications displayed on the tab window 1420 or may drag and drop theobject 1430 on an execution screen 1450 of the application displayed onthe tab window 1420.

In this regard, the dragging and dropping may correspond to convertingthe object 1430 into a floating object 1460 if the user long presses theobject 1430 and dragging and dropping the floating object 1460 to thelocation of objects 1440 indicating the titles of the applications orthe execution screen 1450 of the application.

The device 2200 executes data corresponding to the object 1460 movedaccording to a received user input (for example, drag and drop) in theapplication included in the tab window 1420. The device 2200 outputs anexecution screen of the executed application on the terminal screen. Forexample, if the moved data is a photo file, and the application includedin the tab window 1420 is an image viewer, the device 2200 outputs aphoto on an execution screen of the image viewer.

Referring to FIG. 14B, an example in which the user simultaneouslyperforms an input that moves the object 1460 indicating the dataincluded in the application executed in the tab window 1410 to theapplication included in the tab window 1420 and an input that changes anapplication that is to be executed among applications included in thetab window 1420 is illustrated.

In more detail, the user may touch one of the objects 1440 indicatingthe titles of the applications included in the tab window 1420 with theuser's other hand while long pressing an object indicating the dataincluded in the application executed in the tab window 1410 andconverting the object into the floating object 1460 with user's handThus, the user may freely select one of the applications having anobject to be moved and included in the tab window 1420.

Referring to FIG. 14C, an example in which the device 2200 moves datawithin the same tab window 1410 is illustrated. The user may drag anddrop the object 1430 indicating the data to objects 1470 indicating theapplications included in the tab window 1410.

For example, if an application currently executed in the tab window 1410is an album application, the user may long press an object indicating aspecific photo on an execution screen displayed on the tab window 1410and convert the object into the floating object 1460. Thereafter, theuser drags and drops the floating object 1460 to a location of one ofthe objects 1470 indicating the applications. Thereafter, the device2200 moves the photo selected based on a user's drag and drop to anotherapplication of the album application.

As described above, the user may move an application or data thatbelongs to one of a plurality of tab windows to another tab window. Theapplication or the data may be moved within one tab window. According tovarious embodiments, a tab window may include an application groupincluding heterogeneous applications. Thus, the user may freely movedata between the heterogeneous applications. The user may freely movethe application or the data between the tab windows including theheterogeneous applications.

FIGS. 15A to 15C illustrate examples in which a device sets or changesenvironments of tab windows according to various embodiments of thepresent disclosure.

A screen for setting the environments of the tab windows is illustratedin FIG. 15A. Titles 1510 of currently generated tab windows and objects1520 indicating applications included in each of the tab windows may bedisplayed on one region of the screen. Objects 1530 for editing (i.e.inserting or deleting) the applications included in the generated tabwindows and an object 1540 for changing a layout of the tab windows maybe displayed on another region of the screen.

Therefore, a user may select the objects 1530 for editing theapplications, thereby freely editing the applications included in thetab windows. The user may select the object 1540 for changing the layoutof the tab windows, thereby freely changing a shape of an alignment ofthe plurality of tab windows.

A screen for editing the applications included in the tab windows isillustrated in FIG. 15B. Objects 1550 indicating applications currentlyinstalled in a terminal may be displayed on one region of the screen.Objects 1560 indicating the applications included in the tab windows maybe displayed on another region of the screen.

The user may drag and drop one of the objects 1550 indicating theapplications currently installed in the terminal and move the object toa region that displays the objects 1560 indicating the applicationsincluded in the tab windows, thereby inserting the applicationcorresponding to the selected object. The user may drag and drop one ofthe objects 1560 indicating the applications included in the tab windowsand move the object to a region that displays the objects 1550indicating the applications currently installed in the terminal, therebydeleting the application corresponding to the selected object.

A screen for setting the layout of the tab windows is illustrated inFIG. 15C. When the plurality of tab windows are selected on one regionof the screen, forms 1570 for aligning the tab windows may be displayedon the screen of the terminal. The user may select one of the forms 1570displayed on the screen, thereby determining a shape of an alignment ofthe plurality of tab windows on the screen of the terminal.

In accordance with the descriptions provided with reference to FIGS. 1to 15C above, the tab window according to various embodiments is a tabview but is not limited thereto. The tab window may be any formindicting applications groups including a plurality of heterogeneousapplications without limitation. As an example, the tab window accordingto various embodiments will be described as the tab view with referenceto FIGS. 16A to 21B below.

The methods of managing the tab windows described with reference toFIGS. 1 to 15C apply to various embodiments that will be described laterwith reference to FIGS. 16A to 21B. In other words, although forms orconfigurations of the tab windows of FIGS. 1 to 15C and those of FIGS.16A to 21B are merely different, the methods described with reference toFIGS. 1 to 15C apply to various embodiments that will be described laterwith reference to FIGS. 16A to 21B.

FIGS. 16A and 16B illustrate examples in which the device 2200 outputs atab window 1610 on a terminal screen in a card view form according tovarious embodiments of the present disclosure.

Referring to FIG. 16A, the tab window 1610 in the card view form isdisplayed on the terminal screen. Titles of applications included in thetab window 1610 may be displayed 1620 on a predetermined region of thetab window 1610. When one of the applications included in the tab window1610 is executed, the device 2200 may display an execution screen 1630of the executed application at the very front.

Referring to FIG. 16B, a plurality of applications may be executed amongthe applications included in the tab window 1610. In this case, thedevice 2200 may split the tab window 1610 and display execution screens1641, 1642, 1643, and 1644 of the executed applications.

FIGS. 17A and 17B illustrate examples in which the device 2200 executesa tab window in a card view form when an application is executedaccording to various embodiments of the present disclosure.

Referring to a left figure of FIG. 17A, an execution screen 1710 of theapplication is displayed on a terminal screen. In this case, a user mayselect an object 1721 included in an application tray 1720 that isdisplayed on a predetermined region of the terminal screen. In thisregard, the object 1721 is an object indicating one of applicationsinstalled in a terminal. For example, the user may select the object1721 by touching the object 1721 included in the application tray 1720.

Referring to a right figure of FIG. 17A, the device 2200 receivesselection information of the user and executes the application indicatedby the selected object 1721. The device 2200 adds the applicationexecuted by a user's selection to an application group including apreviously executed application. That is, the device 2200 generates thetab window including the two executed applications.

The device 2200 outputs the generated tab window on the terminal screenin the card view form. In other words, the device 2200 may output theexecution screen 1710 of the previously executed application and anexecution screen 1730 of the application executed by the user'sselection as the tab window in the card view form.

Referring to a left figure of FIG. 17B, the execution screen 1710 of theapplication is displayed on the terminal screen. In this regard, it isassumed that the application that displays the execution screen 1710 isincluded in a predetermined application group. In this case, the usermay select a tray handle 1740 displayed on a predetermined region of theterminal screen. For example, the user may select the tray handle 1740by touching the tray handle 1740.

Referring to a right figure of FIG. 17B, the device 2200 receivesselection information of the user and displays the tab window indicatingan application group including the application that displays theexecution screen 1710 on the terminal screen. In this regard, the tabwindow may be displayed on the terminal screen in the card view form,and the device 2200 may display an execution screen 1750 (of the leftfigure of FIG. 17B) of a most recently executed application on theterminal screen at the very front.

FIGS. 18A to 18C illustrate examples in which the device 2200 manages atab window in a card view form based on a user input of up and downscrolling according to various embodiments of the present disclosure.

Referring to FIGS. 18A to 18C, a process in which the device 2200changes a display form of the tab window based on the user input of upand down scrolling is illustrated.

Referring to FIG. 18A, the tab window in the card view form is output ona terminal screen. In this case, a user may scroll down an executionscreen 1810 displayed at the very front. In this regard, scrollingrefers to a gesture that the user continuously touches the terminalscreen in a specific direction while touching the execution screen 1810.

The device 2200 moves and displays the execution screen 1810 in a scrolldirection (i.e. in a lower direction) based on the user scroll input. Inthis regard, the device 220 may differently display a region of anexecution screen 1810 according to intensity, time, or a distance of thescroll input.

Referring to FIG. 18B, the user may scroll an execution screen 1820displayed on the tab window in the lower direction. The device 2200moves and displays the execution screen 1820 in a scroll direction basedon the user scroll input.

Referring to FIG. 18C, an execution screen 1830 of an application at thevery rear of the tab window is displayed on a center of the terminalscreen. That is, when a plurality of applications are included in thetab window, the user repeatedly performs the operations described withreference to FIGS. 18A and 18B, thereby displaying an execution screenof a desired application on the center of the terminal screen. The useradjusts scroll intensity, tile, and distance, thereby freely adjusting asize of an execution screen of an application.

FIGS. 19A to 19D illustrate examples in which the device 2200 manages atab window in a card view form based on a user input of up and down andleft and right scrolling according to various embodiments of the presentdisclosure.

Referring to FIGS. 19A to 19D, a process in which the device 2200changes a display form of the tab window based on the user input of upand down and left and right scrolling is illustrated. In this regard,user scrolling is the same as described with reference to FIG. 18A.

Referring to FIG. 19A, the tab window in the card view form is output ona terminal screen. In this case, a user may scroll an execution screen1910 of a specific application in a left or right direction.

Referring to FIG. 19B, the device 2200 displays a part 1920 of thescrolled execution screen 1910 on the terminal screen based on the userscroll input. In this case, the user may scroll an execution screen ofanother application in the left or right direction.

Referring to FIG. 19C, the device 2200 displays a part 1940 of thescrolled execution screen 1930 on the terminal screen based on the userscroll input. In this case, the user may scroll an execution screen 1950of another application in an upper or lower direction.

Referring to FIG. 19D, the device 2200 displays the execution screens onoriginal locations 1960 and 1970 based on the user scroll input.

FIGS. 20A and 20B illustrate examples in which the device 2200 convertsexecution screens of applications included in a tab window in a cardview form according to various embodiments of the present disclosure.

In accordance with the descriptions provided with reference to FIGS. 18Ato 19D, the execution screens of the applications included in the tabwindow are displayed on a predetermined region of the terminal screen.In other words, the device 2200 may display the execution screens on theterminal screen by changing locations and regions of the executionscreens based on the user scroll input, whereas the device 220 may notdisplay an execution screen of an application on the entire terminalscreen. However, in accordance with a description that will be providedwith reference to FIGS. 20A and 20B below, the device 2200 may displayan execution screen of a specific application on the entire terminalscreen.

Referring to FIGS. 20A and 20B, a process in which the device 2200converts the execution screens of the tab window based on a user gestureinput is illustrated.

Referring to FIG. 20A, the tab window in the card view is output on theterminal screen. In this case, a user may touch an execution screen 2010of a specific application.

Referring to FIG. 20B, the device 2200 displays an execution screen 2020of an application touched based on a user touch input on the entireterminal screen. Thus, even if a plurality of applications included inthe tab window are executed, the device 2200 may display an executionscreen of an application desired by the user on the entire terminalscreen.

FIGS. 21A and 21B illustrate examples in which the device 2200 manages atab window in a card view form based on a user input of a long touchgesture according to various embodiments of the present disclosure.

Referring to FIGS. 21A and 21B, a process in which the device 2200converts execution screens of the tab window based on the user gestureinput is illustrated.

Referring to FIG. 21A, the tab window in the card view form is output ona terminal screen. In this case, a user may long touch an executionscreen 2110 of a specific application. In this regard, long touch refersto a gesture that continuously touches a same point during apredetermined period of time.

Referring to FIG. 21B, the device 2200 displays an execution screen 2120of an application touched based on the user long touch input on apartial region of the terminal screen. The device 2200 displays anobject 2130 indicating a list of other applications included in the tabwindow on another region of the terminal screen.

Therefore, even if a plurality of applications included in the tabwindow are executed, the device 2200 may display an execution screen ofan application desired by the user on a wide region of the terminalscreen. The device 2200 displays a list of other applications includedin the tab window on the terminal screen, thereby notifying the userabout types of the applications included in the tab window.

In accordance with the descriptions provided with reference to FIGS. 16Ato 21B, the tab window in the card view form corresponds to another formof a tab window in the tab view form described with reference to FIGS. 1to 15C. Thus, although not described with reference to the figures, themethod of moving the applications or the data described above may beperformed in the same way. The device 2200 may apply the method ofstoring the information regarding the tab window described above to thetab window in the card view form in the same way.

FIG. 22 is a block diagram of elements of the device 2200 according toan embodiment of the present disclosure.

Referring to FIG. 22, the device 2200 according to various embodimentsof the present disclosure includes an input unit 2210, a groupgenerating unit 2220, an execution unit 2230, a frame changing unit2240, an output unit 2250, a control unit 2260, and a storage unit 2270.

The device 2200 of FIG. 22 includes elements for performing the methodsof managing the tab windows described with reference to FIGS. 1 to 21B.Thus, although omitted below, the descriptions provided with referenceto FIGS. 1 to 21B may apply to the elements of FIG. 22.

The input unit 2210 receives a user input to the device 2200. A user mayperform a gesture of touching a predetermined location on a terminalscreen. The input unit 2210 may receive the user input according to theuser gesture. The input unit 2210 may receive the user input by using aninput tool such as a keypad of a terminal, a keyboard and a mouse thatare connected to the terminal, and a stylus. The input unit 2210 maydetermine which part of which tab window the user has touched based onthe location of the terminal screen touched by the user. For example,the input unit 2210 may determine whether an object (for example, anicon) for displaying a list of applications has been touched on a tabwindow.

The group generating unit 2220 generates an application group includingan application corresponding to the selected object according to thereceived user input. In this regard, the application group refers to aset of applications included in one tab window.

The application group may include a plurality of heterogeneousapplications. For example, the heterogeneous applications includeapplications having different execution objects or applications whichare different in processes for executing the applications.

The execution unit 2230 executes the applications included in the tabwindow according to the user input. When a plurality of tab windows areoutput on the terminal screen, and the input unit 2210 receives a userinput to execute applications included in each of the tab windows, theexecution unit 2230 may simultaneously or sequentially perform theapplications according to the user input.

The execution unit 2230 may execute the application included in one ofthe tab windows, and execute data included in the executed applicationin the application included in another tab window. A detaileddescription of the operation of the execution unit 2230 is the same asdescribed with reference to FIGS. 12 to 14C above, and thus thedescription thereof will not be repeated here.

The frame changing unit 2240 changes locations of the tab windowsaccording to the user input or reduces or increases regions thereof. Adetailed description of the operation of the frame changing unit 2240 isthe same as described with reference to FIGS. 8 to 9C above, and thusthe description thereof will not be repeated here.

The output unit 2250 outputs a display window including at least one ormore objects on the terminal window. The output unit 2250 may output thetab window indicating the application group on the terminal screen. Theoutput unit 2250 may output the tab windows on the terminal screen. Inmore detail, the output unit 2250 may output another tab window on asecond region distinguished from a first region that displays one tabwindow on the terminal screen.

The output unit 2250 may output an execution screen of the applicationexecuted by the execution unit 2230 on the terminal screen. In moredetail, the output unit 2250 may output an execution screen of theapplication included in the tab window on the terminal screen. In thisregard, the execution screen may be displayed on at least a part of aregion of the terminal screen that displays the tab window.

The output unit 2250 may reflect the locations or regions of the tabwindows changed by the frame changing unit 2240 and output the changedtab windows on the terminal screen.

The storage unit 2270 stores information regarding the tab windows. Inthis regard, the information regarding the tab windows includes a listof the applications included in the application group or the regions ofthe tab windows. In more detail, the storage unit 2270 storesinformation regarding the applications included in the application groupor locations and sizes of the tab windows displayed on the terminalscreen.

When an application or data included in one of the tab windows is movedto another tab window, the storage unit 2270 may renew and store theinformation regarding the tab windows based on the moved application ordata.

The storage unit 2270 may store the locations and the regions of the tabwindows at a time when execution of the tab windows is terminated. Thestorage unit 2270 may store types (for example, titles) of theapplications displayed on the tab windows and execution screens of theapplications at the time when execution of the tab windows isterminated.

The control unit 2260 controls the input unit 2210, the group generatingunit 2220, the execution unit 2230, the frame changing unit 2240, theoutput unit 2250, the control unit 2260, and the storage unit 2270 toallow the device 2200 to perform various operations for managing the tabwindows.

The input unit 2210, the group generating unit 2220, the execution unit2230, the frame changing unit 2240, and the output unit 2250 maypartially or wholly operate via a software module but are not limitedthereto. A part of the input unit 1100 may operate via hardware.

At least a part of the input unit 2210, the group generating unit 2220,the execution unit 2230, the frame changing unit 2240, and the outputunit 2250 may be included in the control unit 2260. The input unit 2210,the group generating unit 2220, the execution unit 2230, the framechanging unit 2240, the output unit 2250, and the control unit 2260 mayoperate via one processor but are not limited thereto.

FIG. 23 is a block diagram of an example of a window grouping managementarchitecture 2300 used by a device to manage a tab window a according toan embodiment of the present disclosure.

Referring to FIG. 23, the architecture 2300 may include an applicationframework 2310 and a manager service 2320. The application framework2310 may be present separately from the manager service 2320.

The architecture 2300 of FIG. 23 includes the elements for performingthe methods of managing the tab windows described with reference toFIGS. 1 to 21B above. Thus, although omitted below, the descriptionsprovided with reference to FIGS. 1 to 21B may apply to the architecture2300 of FIG. 23.

The application framework 2310 performs a request according to a userinput and acts as a user interface (UI). In more detail, the applicationframework 2310 may include an application (app) list manager 2312, anapp window manager 2314, and a tab window manager 2316.

The app list manager 2312 displays graphic images on a terminal screenby using values set by a tab set application described with reference toFIGS. 15A to 15C above. In more detail, the app list manager 2312 setsand manages an icon and a layout of an application group set by the tabset application and sizes of tab windows as a list.

When the app list manager 2312 receives an input to execute anapplication from a user, the app list manager 2312 requests a specifictab window to execute the application. In more detail, when the app listmanager 2312 receives the input to execute the application, the app listmanger 2312 requests the tab window to execute the application based onthe set list.

When an interaction occurs in a tab or between tabs, the app windowmanager 2314 requests the manager service 2320 to perform an actioncorresponding to the occurred interaction. In more detail, when an eventoccurs, such as a location change of the tab window, resize (forexample, reduction or expansion) of the tab window, drag and drop of anobject indicating an application included in the tab window, a movementof the application or data, etc., the app window manager 2314 requests atab history manager 2326 to renew stored information based oninformation regarding the occurred event.

The tab window manager 2316 acts as an interface that transmits allrequests (for example, an UI, an event, etc.) according to a user inputrelating to the tab window from the app list manager or the app windowmanager 2314 to the manager service 2320.

The manager service 2320 renews information regarding the tab windowaccording to a user request and moves the application or the databetween the tab windows. In more detail, the manager service 2320 mayinclude a tab status update manager 2322, a data interaction manager2324, and a tab history manager 2326.

The tab status update manager 2322 transmits the information regardingthe tab window received through the tab window manager 2316 to the tabhistory manager 2326. In more detail, the tab status update manager 2322acquires the information regarding the tab window via the tab historymanager 2326. When a status of the corresponding tab window is changed,the tab status update manager 2322 requests the tab history manager 2326to renew the stored information. In this regard, a change in the tabwindow includes the location change of the tab window, the resize of thetab window, the drag and drop of the object indicating the applicationincluded in the tab window, the movement of the application or the data,etc.

When the movement of the application or the data is requested betweenthe tab windows or in the tab windows, the data interaction manager 2324floats the corresponding application or the data and moves theapplication or the data according to the user input. If the applicationor the data is completely moved, the data interaction manager 2324notifies the tab history manager 2326 that the information regarding thetab window has been changed. The tab history manager 2326 is storagethat stores and renews every piece of information regarding the tabwindows. In this regard, the information regarding the tab windowsincludes an order of the tab windows, a list of the applicationsincluded in the tab windows, sizes of execution screens, locations ofobjects indicating the applications, etc. If the information regardingthe tab windows is requested to be renewed according to a user input,the tab history manager 2326 renews the information regarding thecorresponding tab window and transmits the renewed information to theapplication framework 2310.

The application framework 2310 outputs a change corresponding to theterminal screen by using the transmitted information.

A non-transitory computer-readable recording medium may be an arbitraryavailable medium accessible by a computer, and examples thereof includeall volatile and non-volatile media and separable and non-separablemedia. Further, examples of the non-transitory computer-readablerecording medium may include a computer storage medium. Examples of thecomputer storage medium include all volatile and non-volatile media andseparable and non-separable medial, which have been implemented by anarbitrary method or technology, for storing information such ascomputer-readable commands, data structures, program modules, and otherdata.

It should be understood that the various embodiments described hereinshould be considered in a descriptive sense only and not for purposes oflimitation. Descriptions of features or aspects within each embodimentshould typically be considered as available for other similar featuresor aspects in other embodiments.

While the present disclosure has been shown and described with referenceto various embodiments thereof, it will be understood by those skilledin the art that various changes in form and details may be made thereinwithout departing from the spirit and scope of the present disclosure asdefined by the appended claims and their equivalents.

What is claimed is:
 1. A method of application grouping performed by adevice, the method comprising: including at least one first applicationselected based on a first input of a user into a first applicationgroup; including at least one second application selected based on asecond input of the user into a second application group; displaying,based on a third input of the user, a first view indicating the firstapplication group on a screen; and displaying, based on a fourth inputof the user, a second view indicating the second application group onthe screen using a stored location and a stored region of the secondview and a stored execution screen of an application included in thesecond application group, wherein the including of the at least onefirst application selected based on the first input of the user into thefirst application group comprises: while the first view is displayed onthe screen: displaying an application tray including icons for executingapplications installed in the device on the screen, selecting, based onthe first input of the user, one of the icons included in theapplication tray, including an application corresponding to the selectedicon into the first application group and into a title bar of the firstapplication group, and displaying an execution screen of the applicationcorresponding to the selected icon on at least partial region of thefirst view based on converting a previous execution screen into theexecution screen of the application corresponding to the selected icon,and wherein the stored location and the stored region of the second viewindicates a location and a region of the second view at time when thesecond view ends and the stored execution screen of the applicationincluded in the second application group indicates an execution screendisplayed at the time when the second view ends.
 2. The method of claim1, wherein the first view comprises an execution screen of the at leastone first application included in the first application group and thesecond view comprises an execution screen of the at least one secondapplication included in the second application group.
 3. The method ofclaim 1, wherein the first or second application group comprises aplurality of heterogeneous applications.
 4. The method of claim 1,wherein the second input is an input of touching one of the iconsincluded in the application tray.
 5. The method of claim 1, wherein theincluding of the at least one second application selected based on thesecond input of the user into the second application group comprises:selecting, based on the second input of the user, a first applicationfrom among applications included in the first application group, andmoving, based on a fifth input of the user on the first application, thefirst application from the first application group to the secondapplication group.
 6. The method of claim 1, wherein the including ofthe at least one second application selected based on the second inputof the user into the second application group comprises: selecting,based on the second input of the user, a first application from amongapplications included in the first application group, and based on afifth input of the user on the first application, creating the secondapplication group, and moving the first application from the firstapplication group to the second application group.
 7. The method ofclaim 1, further comprising: storing information about the second view,wherein the information comprises a list of applications included in thesecond application group and information about execution screens of theapplications.
 8. The method of claim 7, wherein the displaying of thesecond view on the screen comprises displaying the second view on thescreen based on the stored information.
 9. The method of claim 1,further comprising: arranging and displaying, in a line on one side ofthe screen, a plurality of objects indicating each of a plurality ofviews.
 10. The method of claim 1, further comprising: selecting a firstapplication from among applications included in the second applicationgroup; selecting data included in the first application; and moving theselected data to a second application from among applications includedin the second application group.
 11. The method of claim 1, furthercomprising: selecting, based on a fifth input of the user, a firstapplication from among applications included in the second applicationgroup; and displaying an entire execution screen of the firstapplication for executing the first application on the screen.
 12. Themethod of claim 1, further comprising: displaying an object fordisplaying a view on an edge of the screen; and while an executionscreen of a first application is displayed on the screen, displaying,based on a fifth input of the user selecting the object for displaying aview, a view indicating an application group including the firstapplication on the screen.
 13. The method of claim 12, furthercomprising: selecting, based on a sixth input of the user, a secondapplication included in the application group; and removing the viewindicating the application group and displaying an entire executionscreen of the second application on the screen.
 14. The method of claim1, the first view indicating the first application group on the screenis adjacent to the second view indicating the second application groupon the screen.
 15. A device comprising: a memory storing one or moreinstructions; and at least one processor configured to execute the oneor more instructions to: include at least one first application selectedbased on a first input of a user into a first application group, includeat least one second application selected based on a second input of theuser into a second application group, display, based on a third input ofthe user, a first view indicating the first application group on ascreen, and display, based on a fourth input of the user, a second viewindicating the second application group on the screen using a storedlocation and a stored region of the second view and a stored executionscreen of an application included in the second application group,wherein, to include the at least one second application selected basedon the second input of the user into the second application group, theat least one processor is further configured to: while the second viewis displayed on the screen: display an application tray including iconsfor executing applications installed in the device on the screen,select, based on the second input of the user, one of the icons includedin the application tray, include an application corresponding to theselected icon into the second application group and into a title bar ofthe first application group, and display an execution screen of theapplication corresponding to the selected icon on at least partialregion of the second view based on a conversion of a previous executionscreen into the execution screen of the application corresponding to theselected icon, and wherein the stored location and the stored region ofthe second view indicates a location and a region of the second view attime when the second view ends and the stored execution screen of theapplication included in the second application group indicates anexecution screen displayed at the time when the second view ends. 16.The device of claim 15, wherein the first view comprises an executionscreen of the at least one first application included in the firstapplication group and the second view comprises an execution screen ofthe at least one second application included in the second applicationgroup.
 17. The device of claim 15, wherein the first or secondapplication group comprises a plurality of heterogeneous applications.18. The device of claim 15, wherein, to include the at least one secondapplication selected based on the second input of the user into thesecond application group, the at least one processor is furtherconfigured to: select, based on the second input of the user, a firstapplication from among applications included in the first applicationgroup, and move, based on a fifth input of the user on the firstapplication, the first application from the first application group tothe second application group.
 19. The device of claim 15, wherein, toinclude the at least one second application selected based on the secondinput of the user into the second application group, the at least oneprocessor is further configured to: select, based on the second input ofthe user, a first application from among applications included in thefirst application group, and based on a fifth input of the user on thefirst application, create the second application group and move thefirst application from the first application group to the secondapplication group.
 20. A non-transitory machine-readable mediumcontaining instructions, that when executed by at least one processor,cause the at least one processor to perform: including at least onefirst application selected based on a first input of a user into a firstapplication group; including at least one second application selectedbased on a second input of the user into a second application group;displaying, based on a third input of the user, a first view indicatingthe first application group on a screen; and displaying, based on afourth input of the user, a second view indicating the secondapplication group on the screen using a stored location and a storedregion of the second view and a stored execution screen of anapplication included in the second application group, wherein theincluding of the at least one first application selected based on thefirst input of the user into the first application group comprises:while the first view is displayed on the screen: displaying anapplication tray including icons for executing applications installed ina device on the screen, selecting, based on the first input of the user,one of the icons included in the application tray, including anapplication corresponding to the selected icon into the firstapplication group and into a title bar of the first application group,and displaying an execution screen of the application corresponding tothe selected icon on at least partial region of the first view based onconverting a previous execution screen into the execution screen of theapplication corresponding to the selected icon, and wherein the storedlocation and the stored region of the second view indicates a locationand a region of the second view at time when the second view ends andthe stored execution screen of the application included in the secondapplication group indicates an execution screen displayed at the timewhen the second view ends.